Description

Closes #3723 by making these changes:

• Update styling in the az_card_title_hover CSS library to target linked card titles.
• Attach the az_card_title_hover library to any Cards paragraph with a card that has a link.
• In the card theme template, add the text-reset class to all linked titles (since we can take care of this styling with a Bootstrap class).

Related issues

• Card title on image is red when the card is not clickable #3723

How to test

Probo review site: https://7b5e2985-cedf-4a13-ab91-3a35916c835d--pr-3729.probo.build

1. Create a page with four Cards paragraphs to test the following:
   • Card title style: Title on image, card title added, link added to Link URL and Link Title
   • Card title style: Title on image, card title added, no link
   • Card title style: Title within card, card title added, link added to Link URL and Link Title
   • Card title style: Title within card, card title added, no link
2. Save the page and confirm that the titles are white on the card image and black within cards. Title links should have an underline on hover.
3. Edit the page again and add additional Cards paragraphs with the "Clickable cards" checkbox checked.
4. Confirm that the styling of the initial cards hasn't changed and the styling of the new clickable cards is correct.

Test page with all steps completed: https://7b5e2985-cedf-4a13-ab91-3a35916c835d--pr-3729.probo.build/brian-test-page

Types of changes

Arizona Quickstart (install profile, custom modules, custom theme)

• Patch release changes
  • Bug fix
  • Accessibility, performance, or security improvement
  • Critical institutional link or brand change
  • Adding experimental module
  • Update experimental module
• Minor release changes
  • New feature
  • Breaking or visual change to existing behavior
  • Upgrade experimental module to stable
  • Enable existing module by default or database update
  • Non-critical brand change
  • New internal API or API improvement with backwards compatibility
  • Risky or disruptive cleanup to comply with coding standards
  • High-risk or disruptive change (requires upgrade path, risks regression, etc.)
• Other or unknown
  • Other or unknown

Drupal core

• Patch release changes
  • Security update
  • Patch level release (non-security bug-fix release)
  • Patch removal that's no longer necessary
• Minor release changes
  • Major or minor level update
• Other or unknown
  • Other or unknown

Drupal contrib projects

• Patch release changes
  • Security update
  • Patch or minor level update
  • Add new module
  • Patch removal that's no longer necessary
• Minor release changes
  • Major level update
• Other or unknown
  • Other or unknown

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My change requires release notes.